xsm/evtchn: never pretend to have successfully created a Xen event channel
authorAndrew Cooper <andrew.cooper3@citrix.com>
Tue, 20 Jan 2015 09:42:26 +0000 (10:42 +0100)
committerJan Beulich <jbeulich@suse.com>
Tue, 20 Jan 2015 09:42:26 +0000 (10:42 +0100)
commit09aa4759faa29c1fe735266de4c79f17329bd67b
tree70ecbc0ea891e9d698e492fa6ae2771dca186465
parentedfd64ea799cd4d29c2efc2d5961ee68ca5fc022
xsm/evtchn: never pretend to have successfully created a Xen event channel

Xen event channels are not internal resources.  They still have one end in a
domain, and are created at the request of privileged domains.  This logic
which "successfully" creates a Xen event channel opens up undesirable failure
cases with ill-specified XSM policies.

If a domain is permitted to create ioreq servers or memevent listeners, but
not to create event channels, the ioreq/memevent creation will succeed but
attempting to bind the returned event channel will fail without any indication
of a permission error.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
xen/common/event_channel.c